LocalTV Remote

How do I fix a rejected LocalTV pairing code?

Read the six-digit code on the PC's current LocalTV Remote pairing page and enter those digits on your phone. If the phone says "Pairing failed," check whether you opened an old PC page or whether the browser tried to restore a saved session before treating it as a new code problem.

A rejection means the phone reached a controller but did not authenticate. That differs from a phone that cannot open the controller address at all. The PC app shows both a QR code and a pairing code, while the phone may remember a previous code and session in its browser. Start with the PC you actually intend to control, especially if more than one computer runs LocalTV Remote.

Check the code you entered

  1. Look at the active PC pairing page. Open LocalTV Remote on the Windows PC and read the six digits shown below its QR code. Do not use a code copied from another PC or typed from memory.
  2. Correct the phone field. On the phone's pairing screen, replace any prefilled digits with the six digits on that PC, then tap Connect. The browser may have filled the field from an earlier connection.
  3. Stop after repeated failures. The server limits failed authentication attempts on a connection. If the code is still rejected, check the page and device below rather than tapping Connect repeatedly.

Replace an old pairing page

If the PC page was left open while the network changed, it may show an address your phone should no longer use. Close that old page, open the current LocalTV Remote pairing page on the intended PC, and scan its QR code again. If the QR opens a different computer, return to the correct PC and use its displayed address and code. The code is derived from the Windows machine and user identity; it is not a timer-based code that expires just because the page is old. A stale page matters because its address or PC context may be wrong.

If the current QR address does not open on the phone, use the manual connection guide or check the local-network troubleshooting steps. A page that never loads needs a network fix before any pairing code can be checked.

Recover from an invalid saved session

The phone browser stores a session token after a successful pairing and may try to reconnect with it later. If that token is no longer recognized, the controller sends its saved code as a fallback when available. A failed authentication clears the saved token and returns the phone to the pairing screen. Overwrite the prefilled code with the digits on the current PC page, then connect again. If no code appears, enter it manually. This is a new pairing attempt, not a way to revoke another phone's access.

For a phone that pairs but later loses control, see the disconnecting remote guide. For initial installation and QR setup, use the phone-to-PC setup guide.

Limits to keep in mind

LocalTV Remote pairs on the local network; this guide does not enable internet control. The current phone and PC screens do not offer a per-device revoke button. Do not share your PC's pairing address and code with people you do not want to connect. If a code is correct but the phone never reaches the controller, investigate the network rather than changing the code.

Get LocalTV Remote for Windows

Reviewed 2026-09-25. Code display comes from host-page.ts; code validation, failed-attempt handling, and trusted sessions are in remote-control-server.ts; browser storage and reconnection are in controller.js.